Peer-to-peer email with video and advertising aspects

ABSTRACT

A Peer-to-Peer (“P2P”) email and social networking system for use by plural users to exchange emails and attachments includes a mesh network that includes plural node computers, each running a P2P email client, and each constructed to transmit and receive emails. The emails are stored in mailboxes residing on each node computer, and may be encrypted during transmission, and may remain encrypted while stored at each node computer.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a non-provisional of U.S. Patent Application Ser.No. 61/381,988, filed Sep. 12, 2010 and entitled “Peer-to-Peer Emailwith Video and Advertising Aspects”, the disclosure of which is hereinincorporated by reference.

This application also incorporates by reference in their entirety, forall purposes, U.S. Patent Application Publication Nos. 2010/0031333 and2009/0144380.

BACKGROUND

Existing email systems may be centrally controlled. Simple MailTransport Protocol (“SMTP”) is the de facto standard used on theinternet today. A first SMTP server (e.g., mail.yin.com) may receiveemail messages from SMTP clients (e.g., Microsoft® Outlook, Mozilla®Thunderbird) executing on computers in the first SMTP server's domain.The email messages may include one or more recipient email addresses(e.g., john@yang.net). The first SMTP server may route the receivedmessages to a second SMTP server on the intended recipient's domain(e.g., mail.yang.net) using known systems such as the domain name system(“DNS”). After receiving the email message, the second SMTP server maydeliver the email messages to the intended recipient's mailbox, whichmay be stored on the second SMTP server and made available to theintended recipient over the network.

SMTP servers may be configured to restrict the size of attachments whichmay be sent with an email message. Other SMTP servers may limit theamount of storage space (i.e., the size of a mailbox) allocated to auser to store emails and attachments. Still other SMTP servers may notprotect or offer the capability of protecting emails and attachmentsassociated therewith from malicious or otherwise unintended recipients,either locally or while in transit over a computer network.

In addition to the above, unsolicited advertising emails (“SPAM”) areubiquitous on the Internet. It is estimated by some that as of 2007, 90billion SPAM messages are sent every day, and that so-called “abusiveemail” accounts for up to 85% of incoming mail in a given email inbox.

Moreover, existing email systems exhibit various inefficiencies. Forinstance, centralized email server farms are estimated to consume overtwo billion dollars worth of energy annually around the world. Inaddition, current methods of encoding attachments involve the use ofbase64, which encodes attachments as 7-bit representations, rather thantraditional 8-bit. Base64 introduces approximately 30% of overhead toeach attachment sent. Some estimate that attachments make up 80% ofemail traffic on the Internet. CPU cycles are also required to performthis encoding on the sending user's computer, as well as perform thedecoding on the recipient user's computer. This processing inefficiencyfor changing encoding of attachments from 8-bit to 7-bit and back to8-bit is a material significant overhead for large files such as HDvideos.

Email users often desire to exchange video files, but video files,including high resolution video files suitable for large screens and HDdisplays such as HD video, blu-ray video, Imax, and 3D video files,typically are quite large, and as noted above, many email systems willnot permit the exchange of attachments beyond a certain size. A meter orother indicator of the progress of sending and delivery in the emailuser interface is a feature of the client interface of the invention.This feature allows the user to see the progress of sending andreceiving large file so that they do not become confused as to thestatus of the delivery. Playing the incoming file, such as an HD videofile, as it is being delivered is also desirable, and the inventionpermits that to occur, so that when a large video file is sent, the usercan play it during the process of arriving, and play it to conclusionwhile the rest of it is delivered, all in high resolution on a largeformat display such as an HD television or display. Using those types ofdisplays will also afford the use of video advertisements includinglarge-file, high-resolution video advertising whether delivered orstreamed, paid delivery services, and other revenue-generating aspectsinto video file exchange.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an example email system.

FIGS. 2A-E depict an email transmission on a system where the sender andthe intended recipient are both online simultaneously.

FIGS. 3A-H depict an email transmission on a system where the intendedrecipient is offline.

FIG. 4 depicts an example method of preventing unsolicited emails.

FIG. 5 depicts a computer using webmail from a remote location to obtaina user's email from his or her computer.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

A Peer-to-Peer (“P2P”) email and social networking system is providedfor use by a plurality of users to exchange emails and attachments. Sucha system may be controlled by one or more central servers, or it may becontrolled by decentralized services distributed over a mesh network.Such a mesh network may comprise a plurality of node computers, eachrunning a P2P email client according to the present disclosure. Nodecomputers may be alternatively referred to as “peers.” Emails may bestored in mailboxes residing on each node, rather than centrallylocated. The system may encrypt emails during transmission, and theemails may remain encrypted while stored at each node computer.

In some embodiments, the system may allow the user of each node computerto configure her email client with the user's interests (e.g.,kayaking). Those interests may be communicated to a central server ordecentralized distributed service, where they may be associated with theuser's email address, so that potential advertisers may search byinterest type, and send solicited emails to users associated with thesearched-for interest types. Similarly, a user's or users' groupprofiles and demographics are known, that information may driveadvertisements, or the file type and size in an attachment, fordelivered-content services to users. If that information is unknown, asis the case for user-generated email with an attachment, also known asuser-generated content, advertisements may be driven separately ortogether, combining knowledge about user profiles and attachment oremail-message-content type and topical nature, keywords, popularity onthe network or metadata.

With or without a media player integrated into the email clientsoftware, the system may require users to observe advertisements,without being able to skip or delete them and, if the user forwards thesame message and attachment to another recipient(s), those subsequentrecipient(s) will also see the advertisement. The associated revenue fordisplaying the advertisement to the recipients in suchsuper-distribution continues to accrue to the provider of the P2P emailand social networking system.

In the social networking aspects of the invention, the agent isconstructed to communicate the profile to the company to drivedemographic ads, and also to synchronize contact updates, and to shareout social information, miniblogs, photos, videos, articles, blogs,etc., in a decentralized networking manner.

There is a need to import contacts into the p2p email and social networksystem so that users can begin to more easily email and otherwisecommunicate with desired contacts. The system of the invention isconstructed to use integrated, unified messaging capabilities, andembodiments include utilizing telephony, video telephony and chat,blogging, instant messaging, and tweeting, to socialize them.

The invention is constructed to support social-media sharing and isconstructed to enable users to email large, rich media files such thatthey can view, play and prioritize the content as it is being delivered,and can communicate with a back channel, such as a chat orinstant-messaging paths. The invention may also be constructed to enablesender and recipient to chat on a back channel, or call each other aboutthe receipt of information to discuss it, such as to discuss a photo, toinform about receiving a large video, or to confirm receipt of the largevideo.

The invention may also be constructed to enable users to search among agroup or other users on the P2P email and decentralized social networksystem. The invention may also be constructed to enable groups to formaround different activity and interest types.

Embodiments of the invention may be constructed to support simpleuploading to sites for traditional online centralized photo, video, orsocial sharing, completing the UGC loop in a triangle—direct to eachother and up to and from sharing sites. In other embodiments, the systemmay be configured to provide remote access to the user's local emailwhen the user is away from her local computer. Such access may beprovided via a webmail webpage interfacing via a secure tunnel to theuser's local email store.

FIG. 1 depicts an example P2P email system 10 comprising node computerssuch as sender 20 and recipient 30. Sender 20 may be a computercontrolled by a first user intending to send an email message to arecipient 30. Recipient 30 likewise may be a computer controlled by asecond user who is the intended recipient of the email message. Sender20 and recipient 30 may be connected by a network 40. Sender 20 mayinclude an email client 22, a local email store 24, and an email agent26. Recipient 30 likewise may include an email client 32, a local emailstore 34, and an email agent 36.

Network 40 may be a local or wide-area computer network, including theInternet. The P2P email system 10 may be controlled by components onnetwork 40, such as decentralized distributed services 42 includingidentity manager 44, presence manager 46, delivery manager 48, andcontact store 49, as well as cache servers 50. The distributed services42 will be described in further detail below. While decentralizeddistributed services 42 are shown having the four components 44, 46, 48and 49 as being separate, these components may alternatively reside on asingle server, and there may be more than one server hosting one or moreof these services. Moreover, additional services which are not shown(e.g., a gateway server for sending emails to traditional email domains)may also be included.

Email clients 22 and 32 may include user interfaces resemblingtraditional email clients (e.g., Outlook, Thunderbird), and may beconfigured to allow a user to draft, send and receive P2P emails. Emailclients 22 and 32 may further include interfaces allowing a user toselect interests (e.g., kayaking, dating), or contact demographic andinterest profile information, or browsing history data, which may becommunicated to decentralized distributed services 42 so that potentialadvertisers may communicate solicited emails to clients 22 and 32, aswill be discussed further below.

Local email stores 24 and 34 may be portions of memory (e.g., on a localhard drive) which may be used to store email messages and associatedattachments. In other words, local email stores 24 and 34 may servesimilar roles as mailboxes on traditional SMTP servers. Messages storedin local email stores 24 and 34 may be encrypted. The amount of spaceallocated to a user may be configured, and in some embodiments may belimited only by the computer's storage capabilities. In addition toemails and attachments, local mail stores 24 and 34 may store interestinformation (a.k.a. user metadata), user contacts (e.g., the user'sfriends residing on P2P email system and elsewhere), user profiles(e.g., photos available for viewing, whom may view the photos, personalinformation and to whom it is available), group membership (e.g., openor closed groups of users of P2P email system 10 having commoninterests/metadata/contacts) or the like. Interest information,contacts, profiles and other similar information may be configured by auser using email clients such as 22 or 32.

Email agents 26 and 36 may be processes executing on node computers suchas sender 20 or recipient 30 forming the P2P network. While a computersuch as sender 20 or recipient 30 is connected to network 40 and isexecuting its email agent (26 or 36), that computer may be considered‘online’ for purposes of the P2P network and this discussion.

Contact store 49 may be a central server or servers, or it may be aservice distributed among various nodes in the P2P email system 10. Itmay contain information allowing peers on P2P email system 10 to locateother peers, including information similar to that stored in local emailstores described above like interest information, contacts, metadata,social profile, demographics, location, group membership, and the like.Peers may be searched at contact store 49 using various search values,such as interests, group membership, friendship networks, personalprofiles, and the like. In some embodiments, users may synchronizeinformation stored in their local email stores 24, 34 such as metadata,profiles, and contacts with information contained in contact store 49.In other embodiments where contact store 49 is a service distributedamong various nodes, there may be a central contact store (not shown)which is configured to synchronize all nodes on which contact store 49is contained.

Cache servers 50 may comprise one or more computers on network 40 whichmay be used as intermediate points in email communications betweencomputers such as sender 20 and recipient 30. Cache servers 50 may beconfigured to cache at least a portion of email messages, as well asattachments thereto. In some embodiments, each cache server may be anode computer, similar to sender 20 or receiver 30, forming another peeron the P2P system. Additionally or alternatively, cache servers 50 maybe specialized computers maintained specifically for the purpose ofcaching emails. In some embodiments, cache servers may only cacheattachments having a size smaller than a predetermined size (e.g., <50Megabytes).

A given email message in transition between sender 20 and recipient 30may be stored at a number of cache servers 50 while awaiting delivery,providing redundancy and high availability of the email message torecipient 30 in case some of the cache servers become unavailable (e.g.,go offline). Moreover, cache servers 50, which may simply be peers ornode computers on P2P system 10, may be configured to forward emailmessages to other intermediate peers closer to the recipient'sdestination. The cache servers may also be configured to forward emailmessages to multiple recipients' destinations, particularly in the caseof a permitted opt-in delivery of content or advertisement in emailmessages to a large group of recipients. Additionally or alternatively,if a given cache server is going to go offline, it may forward copies ofits stored pending email messages/attachments and/or notify the P2Pemail system of the email's new location.

The P2P email system 10 will now be explained by example. An exampleemail communication between two node computers 20 and 30, which areonline simultaneously, is shown in FIGS. 2A-E. In step 1 of FIG. 2A,email client application 22 submits an email message created by a firstuser to email agent 26. In step 2 of FIG. 2B, email agent 26communicates with identity manager 44 to verify the recipient emailaddress(es) contained in the email message, and to obtain one or morepublic keys corresponding to the verified email address(es). The publickeys may be used by email agent 26 to encrypt the email message and/orany the message's attachments.

Identity manager 44 may take various forms. In some embodiments,identity manager 44 may be a central database running a hash table orsimilar data structure for relating email addresses to public keys. Inother embodiments, identity manager 44 may be a distributed hash table(“DHT”), such as Content Addressable Network (“CAN”), Chord, Kademlia,Pastry, P-Grid, Tapestry or NeoNet, to name a few. DHTs are a class ofdecentralized distributed systems that provide a lookup service similarto a hash table. They are well-known in the art, and therefore need notbe described further here. Email addresses such as the recipient emailaddress may comprise the names of the hash table, and the value(s)corresponding to each name may be one or more public keys. Email agentssuch as 36 each may possess private keys usable to decrypt messagesencrypted with the one or more public keys.

In step 3 of FIG. 2C, sender email agent 26 may communicate withpresence manager 46 to determine whether recipient 30 is online. Ifrecipient 30 is online, sender email agent 26 may obtain recipient'snetwork address (e.g., IP address), and may indicate in the client userinterfaces network-wide, or within a network sub-group, where sender orrecipient are an existing client contact that the sender and recipientare online or offline, i.e., present or not present

Presence manager 46 may be a central server configured to track thepresence of email clients and make that information available to emailagents such as 26 and 36. Presence manager may be a central server ordecentralized service, implementing various protocols, such as theExtensible Messaging and Presence Protocol (“XMPP”), for real-time ornear-real-time presence information. Jabber Instant Messaging andPresence technology is based on XMPP, and may be used in someembodiments as presence manager 46.

Once sender email agent 26 has obtained the network address of recipient30 from presence manager 46, sender email agent 26 may transmit theemail message and any attachments thereto directly to recipient emailagent 36 in step 4 of FIG. 2D. When recipient email agent 36 receivesthe email message, in step 5 of FIG. 2D, it may store the email message(which may remain encrypted) and attachments thereto in local emailstore 34.

When the user of recipient 30 executes email client 32 to check heremail, in step 6 of FIG. 2E, recipient email client 32 may communicatewith local email store 34 to obtain all recipient's email messages,including the newest message just received, as well as any attachmentsthereto. If the messages are encrypted, email client 32 may use itsprivate key, corresponding to the public key described above, to decryptmessages.

The above discussion describes an email transmission where both sender20 and recipient 30 are online simultaneously. However, there is noguarantee that recipient 30 will be online at the moment sender 30transmits an email message. FIGS. 3A-H and the following discussiondescribe one possible way an email may be transmitted between sender 20and recipient 30 under such a scenario.

In step 100 shown in FIG. 3A, similar to step 1 of FIG. 2A, email clientapplication 22 submits an email message created by a user to email agent26. Similar to step 2 in FIG. 2B, in step 102 of FIG. 3B, email agent 26connects to identity manager 44 to verify the recipient email addressescontained in the email message, and to obtain public keys correspondingto the verified email addresses. And again, in step 104 in FIG. 3C,sender email agent 26 communicates with presence manager 46 to determinewhether recipient 30 is online.

In the previous example, recipient 30 was online, and thereforeavailable to receive the email message and attachments directly fromsender 20. However, in this example, recipient 30 is offline. Therefore,in step 106 of FIG. 3D, sender email agent 24 may communicate themessage body of the email message and any attachments having a size lessthan a predetermined amount to cache servers 50 residing on network 40.In some embodiments, attachments having sizes greater than thepredetermined amount may remain stored locally on sender 20. In step 108of FIG. 3E, sender email agent 26 may notify delivery manager 48 thatthere are pending messages stored in network 40, as well as where thosepending message may be located (e.g., on which cache servers 50 themessage is cached).

In some embodiments, delivery manager 48 may be a central serverconfigured to store information regarding pending P2P email messagesstored in network 40. In other embodiments, delivery manager 48 may be adecentralized service such as a DHT or other similar distributedsystems.

In some embodiments where delivery manager 48 is a DHT, the names may berecipient email addresses, or other email addresses with the file withthe same DHT. The values associated with that data may includeinformation necessary for recipient email agent 36 to obtain pendingemail messages from network 40. Specifically, agent 36 will obtain thoseemail messages from one or more of the nodes with the message, orattachment, on the network nodes concurrently and in pieces in amulti-source manner or swarm-delivery manner. Such information mayinclude address information associated with particular cache servers 50having cached copies of the pending email. The address information maybe a network address of the particular cache servers 50 storing thepending emails, or, if each cache server is merely another node similarto 20 or 30, the address information may be an email address associatedwith each node.

In other embodiments, each email message or attachment may have a uniqueUniversal Resource Name (“URN”). Recipient email agent 36 may benotified of any URNs associated with email messages or attachmentsdestined for recipient 30. A delivery manager 48 implementing a DHT mayuse URNs related to pending email messages and attachments as names, andthe value(s) associated with each URN may be a Universal ResourceLocator (“URL”). The URL may indicate where the email message/attachmentidentified by a URN may be found, as well as what method may be used toobtain the message/attachment (e.g, ftp://www.yin.com/attachment.jpgindicates that the file ‘attachment.jpg’ may be obtained from the domainyin.com using the ftp protocol).

Accordingly, when recipient 30 comes online, in step 110 of FIG. 3F,recipient email agent 36 may communicate with delivery manager 48 todetermine whether there are pending email messages on network 40 whichare intended for recipient 30 and to identify one or more cache servers50, or other email addresses or attachment files, where those messagesare located. In some embodiments, recipient email agent 36 may nextcommunicate with presence manager 44 to determine which of theidentified nodes are currently online and those nodes' networkaddresses.

Next, in step 112 of FIG. 3G, recipient local email store 34 (oralternatively, recipient email agent 36) may communicate with theidentified nodes of the cache servers 50 to retrieve message bodies andattachments having a size less than the predetermined amount describedabove.

Attachments larger than the predetermined size may be obtained from theoriginal sender 30, assuming sender 30 is currently online. If sender 20is not currently online, recipient 30 may periodically query presencemanager 46 so that when sender 20 comes back online, recipient 30 maythen obtain the large attachment directly from sender 20. Alternatively,recipient 30 may obtain that attachment from other email addresses onthe network nodes with the message and or file attachments singularly orin unison as a multisource or swarm delivery. If the sending anddelivery process is interrupted it may smart resume where it left off.

In some embodiments, where local email store 34 or email agent 36 mustdownload multiple emails from cache servers 50, it may prioritize whichemails/attachments will be retrieved first. For instance, an emailclient 32 may provide an interface for a user to edit contacts and sortthem by various criterion (e.g., degrees of separation of friendship,age, etc.). Using this priority information, email client 32 or agent 36may retrieve emails/attachments in the order of which its contacts havebeen sorted by the user. This priority information may be synchronizedwith contact store 49 when convenient.

When the user of recipient device wishes to read the receivedmessage(s), he or she may use recipient email client 32 to view emailmessages, including newly received messages, stored in local email store34 in step 108 of FIG. 3H.

In some embodiments, sender 20 may be configured to verify thatrecipient 30 received the email address. For instance, recipient emailagent 36 may send an acknowledgement to sender 20 once recipient localemail store 34 has received and stored the entirety of the email and anyattachments thereto. Additionally or alternatively, Sender 20 may queryrecipient 30 to determine whether recipient 30 received the message. Insome embodiments, recipient 30 may notify one of the services indecentralized distributed services 42 (e.g., delivery manager 48) that amessage having a particular URN has been delivered. In such a case,sender 20 may verify that the message was received by communicating withthe services 42.

In the P2P email system disclosed herein, some embodiments may beconfigured to prevent unsolicited email and/or provide users with emailsrelated to topics of interest. Turning to FIG. 4, in step 200, anadvertiser 62 of a particular interest (e.g., a kayak manufacturer) orwith a video, image, or audio, or text file attachment containing email,may communicate with decentralized distributed services 42 to uploadadvertisement information, which may be permission based, and mayinclude metadata such as keywords (e.g., kayak) as well as advertisingemails and/or attachments. One common type of advertising attachment isa video advertisement. As will be discussed below, in some embodiments,email clients include video player interfaces for playing video fileattachments, and advertising videos may be assigned to videos based onvideo size, popularity and/or user demographic information, andrecipient may be unable to skip the advertisement.

Email client 22 may include an interface including a list 60 ofselectable interests. A user of email client 22 may choose one or moreinterests from list 60 in step 202, and those choices may becommunicated to decentralized distributed services 42 (e.g., to deliverymanager 48) in step 204. In step 206, email agent 26 may “pull” down theadvertisements uploaded by advertiser 62 in step 200. Note that becausesender 20 indicated interest in kayaks, the email sent in step 206 isnot unsolicited.

In some embodiments, advertisers such as 62 may be charged a fee foreach of their advertisement emails “pulled” from the system 10.Additionally or alternatively, a ratings system similar to those used intelevision (e.g., Nielsen ratings, which are based on the habits of homeTV viewers) may be implemented to ascertain how much a givenadvertisement is “pulled,” for purposes of charging advertisers such as62. In another embodiment, the user may be charged for delivery ofcontent, and delivery may further be into a secure folder, zone, orchannel, which may be spam-free, dedicated to one or a small authorizedgroup of senders, and may be branded to identify it. The deliveredcontent may also share the same secure login as an online secure sitewith the same publisher or vendor of content (media, medical, billingdelivery, etc.), and may be readable or playable online in the securefolder/zone/channel when inside of that location to provide additionalsecurity, digital rights management and content locker protection.

In another aspect, a user who is away from her computer containing herP2P emails may nevertheless wish to access those emails. In traditionalemail systems (e.g., SMTP), such a user may have access to a webmailinterface, which may comprise a HTML page which the user may access witha web browser. The user may enter her login information (e.g., ausername and password), and upon successful authentication, the webpagemay direct the user's web browser to a second webpage which allows theuser to view, manipulate, and create/send new email messages. Thissecond web page may obtain email data from and interface with the samemail server (containing the user's mailbox) which the user wouldnormally log into with her local computer.

Webmail access similarly may be possible in some embodiments of thedisclosed P2P email system 10. Referring to FIG. 5, a user may be awayfrom her computer 20, but may wish to access email on her local emailstore 24 using a remote computer 70. A central server or one of thedecentralized distributed services 42 (such as delivery manager 48) mayinclude a webmail service. In step 300, the user may connect to thewebmail service executing on decentralized distributed services 42 andprovide login credentials to a login webpage. Upon successfulauthentication, the user may be redirected to a second webpage givingthe user email access. Instead of communicating with the user's mailboxon a central SMTP server, however, in step 302, the second webpage maycommunicate with the user's local email store 24 through a secure tunnel72 to the user's computer 20.

Although the above examples only describe the exchange of email messagesbetween two node computers on P2P system 10, those skilled in the artwill understand that communications may occur between plural nodecomputers. Moreover, communications may occur between a node computer onP2P system 10 and a traditional email system (e.g., hotmail, gmail,exchange server, etc.).

For example, one of the decentralized distributed services (e.g., aseparate gateway server which is not shown) may be identified as a mailexchanger (MX) in a DNS. The Gateway server therefore may receive emailmessages/attachments sent from traditional email systems, destined for arecipient residing on the disclosed P2P email system 10, and communicatethose messages to the appropriate recipients using the above-describedmethods (depending on whether the user is online or offline).

Likewise, if a user on a node computer of P2P email system 10 desires tosend an email message to an outside traditional email address, the usermay communicate the message and any attachments to the gateway server.The gateway server may forward the message to the appropriate SMTPserver using MX records in the DNS. In some embodiments, identitymanager 44 may be configured with an index of domains that are part ofP2P email system 10. When sender 20 verifies the email address, such asin step 2 in FIG. 2B or step 102 in FIG. 3B, identity manager 44 maydetermine whether the recipient email address(es) are within the P2Pemail system 10. If manager 44 makes that determination, then theprocess may proceed as described above. If a recipient email address isdestined for an outside domain unrelated to the P2P email system 10,however, sender 20 may be required to forward the email and anyattachments to the gateway server for delivery to the outside domain.

In another aspect of the disclosure, the P2P email system 10 may provideefficient attachment distribution. In some instances, instead of usingbase64 to encode attachments to 7-bit representations, the P2P emailsystem 10 may determine the URLs of attachments and make those URLsavailable through decentralized distributed services 42. For instance,assume sender 20 sends an email message including a large attachment(i.e., too large to be stored on cache servers 50) to recipient 30. Alsoassume recipient 30 is online simultaneously with sender 20. The emailreceived by recipient 30 may not include the large attachment, encodedusing Base64 or otherwise. Instead, the email received by recipient 30may include a hyperlink (URL) to a location on sender 20 containing thelarge attachment, so that recipient 30 may initiate a connection tosender 20 and download the large attachment directly (e.g., using FTP,HTTP, BitTorrent, or other well-known transfer protocols). Theinitiation of the file transfer may not require intervention by the userof recipient 30. Instead, recipient email client 32 may be configured toautomatically initiate the transfer when the user opens the email orattachment.

In another aspect of the disclosure, large attachments such as videofiles may have characteristics such as size and popularity. When a videofile is exchanged using disclosed P2P email systems, one or moreadvertisements (e.g., additional video files) may be assigned to thevideo file based on the size of the video file and/or its popularity.Advertisements also may be assigned to video files based on demographicinformation relating to a sender and/or a receiver of the video file.Demographic information may be obtained from user profiles of the senderand/or receiver. Once an advertisement is assigned to avideo-file-to-be-exchanged, a copy of the advertisement may be sent tothe receiver of the video file. In some instances the receiver may beforced to view the advertisement before being permitted to view thevideo file itself. If the advertisement/message is forwarded to otherrecipients, advertisements may follow it from node to node.

In another aspect of the disclosure, the process of a user whether anexisting member of the system or a new one without the P2P email andsocial networking system, may request, via a link or icon button,delivery of a file from a website, and a software routine on the serverside of the website, or on the server side of the company providing theP2P email and social networking system, then send to the requestor alink for that user to get the system, and to then receive the large filedelivered to them, whether immediately, or at a later date based on thecontact information provided including a legacy email address from theold email system. A recipient would receive a message that they have abig file sent to them, download and install the p2p email and socialnetworking software system, then receive the large file delivery.

For example, if a 25-year-old male in Boston is the receiver of an emailwith a large video file attachment, then an advertisement targetedtowards young men in urban areas may be identified and assigned to theemail. Before the 25-year-old male receiver in Boston is permitted todownload and/or view the video file, he may be forced to view all or aportion of the assigned advertisement, which may be delivered to himusing the same methods as the large video file, which are discussedgenerally above.

P2P email clients such as 22 and 32 in the drawings may include in theiruser interfaces an interface for viewing videos. The email clients maybe configured to start playing a video file on the user interfaceimmediately after the download begins (in a streaming fashion), or theemail clients may be configured to wait until the entire video file isdownloaded before showing the video on the interface. In someembodiments that stream video, email clients may be configured to recordstreaming video. In other embodiments, email clients may be configuredto upload videos to network devices having displays, such as tabletcomputers, HD televisions, smart phones, or to burn a disc to play it ina DVD or CD player and reach an audio or video device in the digitalliving room.

The p2p email and social networking system may also be resident on manyplatforms beyond personal computers, including but not limited to,set-top boxes, network accessible storage devices, cameras, mediaservers and other digital living room gear such as game consoles.

Assigning an advertisement to a video may include embedding anadvertisement within the video, concatenating an advertisement to thebeginning of the video, anywhere in the video, or at the end of thevideo, or simply attaching an advertisement to the email message towhich the video is an attachment. In the latter case, email clients maybe configured to search received emails for attachments that are flaggedas advertisements first, and may force a user to view the advertisementbefore being permitted to view the main video attachment.

Revenue may be generated from the exchange of video files and/or theassignment of advertisements to those video files. For example, if avideo file is stored on the computers of less than 1000 users, then thevideo file may not be assigned an advertisement when exchanged, and thereceiver may not be required to view an advertisement video beforeviewing the video attachment. However, if the video is stored on thecomputers of between 1001 and 99,999 users, then when the video isexchanged, it may be assigned one advertisement intended for arelatively small audience, and receivers may be forced to view thisadvertisement before viewing the video attachment. If the video file ismore widely distributed (e.g., on computers of 100,000 users or more),then another different advertisement that is intended for a wideraudience may be assigned to the video, and receivers may be forced toview this second advertisement before viewing the video attachment.

Advertisers such as 62 may be charged a fee for each of theiradvertisement videos that is assigned to a video-file-to-be-exchanged.Moreover and similar to above, a ratings system similar to those used intelevision (e.g., Nielsen ratings) may be implemented to ascertain howoften a given advertisement video is assigned to videos for purposes ofcharging advertisers such as 62. Additionally or alternatively, P2Pemail clients with video playing interfaces may send out a notificationwhen a user plays a particular advertisement and/or video, and thecorresponding advertiser may be charged at that time.

In some embodiments, a website operator may include a link to a videothat when selected, causes the user to be redirected to a download of aP2P email client such as those described above. The user may downloadand install the client so that the user can receive the video file usingabove-described systems in methods.

In other cases, a website link or icon can be selected that causes anemail to be sent to a user's traditional email account. The email mayinclude a link to a P2P email client, such as those described above, andonce the user follows the link and installs the client, the user may besent an email at the user's P2P email address that includes the videofile as an attachment.

Accordingly, while embodiments have been particularly shown anddescribed with reference to the foregoing disclosure, many variationsmay be made therein. The foregoing embodiments are illustrative, and nosingle feature or element is essential to all possible combinations thatmay be used in a particular application. Where the disclosure recites“a” or “a first” element or the equivalent thereof, such disclosureincludes one or more such elements, neither requiring nor excluding twoor more such elements. Further, ordinal indicators, such as first,second or third, for identified elements are used to distinguish betweenthe elements, and do not indicate or imply a required or limited numberof such elements, and do not indicate a particular position or order ofsuch elements unless otherwise specifically stated.

1. A Peer-to-Peer (“P2P”) email and social networking system for use byplural users to exchange emails and attachments, comprising: a meshnetwork that includes plural node computers, each running a P2P emailclient, and each constructed to transmit and receive emails.
 2. Thesystem of claim 1, wherein emails are stored in mailboxes residing oneach node computer.
 3. The system of claim 1, wherein the emails areencrypted during transmission.
 4. The system of claim 3, wherein theemails remain encrypted while stored at each node computer.